Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0885

reference: 790-tree-1
name: 0885
tree-preservation-order: undefined
790-tpo-1
uprn
address-text
point: POINT (-1.044127 50.865193)
geometry: MULTIPOLYGON (((-1.044085 50.865188,-1.044086 50.865197,-1.044092 50.865204,-1.044102 50.865210,-1.044114 50.865214,-1.044127 50.865216,-1.044152 50.865211,-1.044161 50.865205,-1.044168 50.865197,-1.044170 50.865189,-1.044168 50.865181,-1.044162 50.865173,-1.044153 50.865167,-1.044141 50.865163,-1.044128 50.865162,-1.044115 50.865163,-1.044093 50.865172,-1.044087 50.865180,-1.044085 50.865188)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL